How are you separating Policies from Procedures in PolicyStat?

Hi all,

We’re cleaning up our PolicyStat library, and many documents mix policy (what and why) with procedure (how). We want to:

  1. Give staff a one-click way to see only procedures.
  2. Make it clear to surveyors, on the document and the printed PDF, that a document is a procedure.

How are you handling this? Reference tags, separate Areas, title prefixes, a header line, separate approval workflows or review cycles? Any definitions, templates or lessons learned would be appreciated.

Thank you! Vanessa Ramirez, Compliance Coordinator, Emerus

Hi @vanessa.ramirez, thanks for bringing this up. Currently we do not have a quick way to separate policies from procedures. We have a different templates that are used for creating them, and some departments identify procedures within the title, and others use reference tags. I’m interested to see what others may be doing to help easily identify each type respectively.

As a side note, we also have forms in our PolicyStat library, however they are all kept in a single area titled Forms.

We have a separate area called “SOPs” and all procedure titles start with "SOP - " so that at a glance, staff can tell if something is a SOP (e.g. procedure) versus a policy. Very recently we added an area called “Job Aids”. Our policy on policies clearly defines that job aids are not part of the P&P. Job Aids is where we put the technical info, like the steps to discharge a patient in our EMR and who is responsible for pushing the different buttons. I don’t know if this system would work for a large organization with thousands of policies, but so far, it is working well for us.